Bring back async_cmd_check to check for parallel extension install completion and fix dry-run mode with parallel extensions - #5223
Conversation
1f45a6a to
62f6eb1
Compare
async_cmd_check to check for parallel extension install completion and fix dry-run mode with parallel extensions
Accessing the task would fail as it is never set
62f6eb1 to
21b8c05
Compare
It's true that I don't see why we would reinstate So instead, I think we should:
|
The rpackage easyblock shows that this is a useful hook to check that the async command actually succeeded that simply checking the completion marker of the task doesn't allow: https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/generic/rpackage.py#L335-L337 The base implementation of So I don't see this as a replacement but an enhancement and think we should keep it. |
We currently have this documentation
It is used by rpackage which calls into the super method:
https://github.com/easybuilders/easybuild-easyblocks/blob/e53ee56b0ddce722fb4b37371096b0eabae6cf6f/easybuild/easyblocks/generic/rpackage.py#L335
However it was removed by 36febd8 so the rpackage would crash.
This PR brings it back working together with this callback and the expectations:
self.async_cmd_outputself.async_cmd_task.done()This allows rpackage to work again and makes the implementation match the documentation.
Additionally I found that
--extended-dry-runwould crash:In the dry-run mode the task is never started.
I resolved that by using a dummy result
And finally dry-run did query the dependencies but then didn't use them yielding misleading output.
The fix is straight forward but changes indentation, so the diff looks larger than it is.